System and method for multi-site load-balancing of encrypted traffic

ABSTRACT

A system of redirecting encrypted requests for content at a web site includes the steps of receiving, at a first web site, data enabling secure communication with a client, receiving, at the first web site, a request for content from the client, identifying an alternate web site to service the request from the client and forwarding a communication associated with the request to the alternate web site including forwarding the data enabling secure communication to the alternative web site. Such an arrangement allows a web site to communicate with a client using encrypted packets without having previously set up a tunneled connection, thereby aiding in disaster recovery and providing a facilitating client proximity detection when traffic is encrypted.

FIELD OF THE INVENTION

[0001] This invention relates generally to the field of networking, and more specifically to a system for optimally servicing client requests in a network wherein some of the traffic is encrypted.

BACKGROUND OF THE INVENTION

[0002] As is known in the art, load-balancing solutions are becoming more common to support high-traffic Web sites. Typically high traffic Web sites can't process all requests on a single server. In order to increase the performance of the Web site (where the performance can be measured in response time to requests, among other criteria), one may seek to increase the capabilities of the server supporting the Web site. Rather than move the Web site to a more powerful and expensive hardware, clusters, or farms, of servers are provided, where each of the clusters store mirrored copies of the Web site. As requests are received for access to the Web site, the ‘best’ server cluster is selected to respond to each request. The selection of the ‘best’ server cluster for each web request depends upon a variety of considerations, including the health, user proximity, weights, and response times associated with each of the servers.

[0003] Some technologies that attempt to provide a measure of geographic distribution of Web requests rely primarily on Domain Name System (DNS) techniques, which rely on the DNS server alone or in combination with other logic. For example, round robin DNS techniques map multiple IP addresses to a single DNS host name. As clients resolve the hostname, DNS responds by cycling through the multiple IP addresses mapped to the host name. The DNS technique may be further enhanced by using routing metrics or network distance calculation. Alternatively, sets of IP addresses may be associated with geographically diverse DNS servers. While the DNS techniques provide some load sharing capabilities, they are problematic because they are resource intensive to resolve and are typically incapable of being content aware.

[0004] An improved load balancing approach for high traffic web sites is implemented in the Alteon line of products provided by Nortel Networks, Ltd. The Alteon product line includes Content Directors (CDs), which are designed to route or load balance requests between web sites. Various data is used in determining the client proximity to the available servers and thus where to route requests. This data includes the distance between server and client, the current health of each site, the response time for each site (indicating the relative load at the site), and the availability of content at each site. The CDs are able make client proximity calculations at TCP connection time using a selection of proximity detection methods. Because the CD can make client proximity calculations at TCP connection time, the CD is able to calculate the closest topographical path between the client and each site, rather than having the calculation performed by the client's local DNS server.

[0005] Several of the techniques used by a CD for proximity detection are described in U.S. patent application Ser. No. 09/728,305, entitled “A Method and Apparatus for Discovering Client Proximity”, filed Nov. 30, 2000 by Tenereillo et al. (hereinafter referred to as the Tenereillo patent), incorporated by reference herein. An exemplary method disclosed in the Tenereillo patent is a so-called ‘footrace’ method for determining client proximity. The basic blocks of the footrace method are shown in FIG. 1, and will be described with regard to a client requesting content that is mirrored at three different web sites; Site A, Site B and Site C. Initially, at step 22 the client establishes a set of TCP connections to a Web Site by requesting access to a resource having a certain IP address. At step 24, DNS resolves the domain name to the IP address of one of the sites in the global domain, for example Site A. The global domain is registered in DNS with a unique Fully Qualified Domain Name (FQDN).

[0006] At step 26, the CD at Site A that receives the client's initial request acts as a synchronizing CD, and forwards partially built redirect messages to each participating web site (i.e., web sites which store mirrored copies of the content) including itself. The redirect message includes a local domain field and a response time field. The local domain field indicates the local domain to which future requests for the resource should be redirected. When the synchronizing CD partially builds the redirect messages, it leaves the local domain URL portion of this field empty. The response time field stores a time value indicating when the CDs at the participating web sites should forward their rebuilt redirect message back to the client.

[0007] At step 28, the CD at each web site that receives the partially built redirect message fills in the local domain field with their own local domain URL to provide a rebuilt redirect message. At the precise time indicated by the response time field, the CD at each participating web site forwards the rebuilt redirect message (with modified local domain URL) back to the client. In essence, a footrace ensues, with the participating web site having the fastest response time winning the footrace back to the client. At step 30, the client breaks the TCP connection with the synchronizing web site (Site A, in the above example, assuming Site A did not win the footrace), and initiates a new TCP connection to the local domain URL retrieved in the ‘winning’ redirect message.

[0008] Alternative methods of selecting the most proximate client are also described in the Tenereillo patent, and may include caching the URL of the ‘best’ Web site for client requests and building an HTML page having links between the various Web Site local domain names and the client to permit the client to calculate the round trip time for accessing each local domain.

[0009] However, one problem with the above described method of determining the optimum Web site is that is cannot be used in an environment where encrypted traffic is transferred between a client and a server, since certification and authentication is generally done on a point to point (client/server) basis. Accordingly, it would be desirable to determine a method for load balancing web site resources in a network including encrypted traffic.

SUMMARY OF THE INVENTION

[0010] According to one aspect of the invention, a method of balancing accesses to a resource in a network having encrypted traffic includes the step of storing, at a first web site storing the resource, an address of another web site storing a copy of the resource. The method further includes the step of receiving, at the first web site, a request from a client for the resource, the step of receiving including receiving data enabling secure communication with the client. The method further includes the step of forwarding, by the first web site, a redirect packet to the another web site, the step of forwarding including the step of modifying the redirect packet using the data enabling secure communication with the client.

[0011] According to another aspect of the invention, a data center storing a plurality of resources includes a table for storing, for at least one resource, an address of an alternate data center storing a copy of the resource. The data center also includes an interface for establishing a secure communication path with a client device and a storage mechanism for storing data enabling secure communication with the client device. The data center further includes a packet builder for building redirect packets for the mirrored web site, the redirect packets comprising the address of the alternate data center and being modified by the data enabling secure communication with the client device.

[0012] With such an arrangement, client proximity calculations may be easily performed to aid in web site load balancing in an encrypted network environment.

BRIEF DESCRIPTION OF THE DRAWINGS

[0013]FIG. 1 illustrates exemplary steps that are used in a prior art footrace method for selecting an optimal web site to service a client request;

[0014]FIG. 2 is a block diagram of a system according to the present invention for web site load balancing of encrypted traffic;

[0015]FIG. 3 is a flow diagram illustrating exemplary steps performed during establishment of a secure communication between a client and a web site using Secure Socket Layer (SSL) technology;

[0016]FIG. 4 is a block diagram illustrating exemplary components that may advantageously be included in a Content Director (CD) of the present invention;

[0017]FIG. 5 is a flow diagram illustrating a method that may be used to redirect encrypted packets for disaster recovery purposes;

[0018]FIG. 6 is an illustrative block diagram showing the flow of packets in the process described in FIG. 5;

[0019]FIG. 7 is a flow diagram illustrating a method of load balancing encrypted traffic; and

[0020]FIGS. 8a, 8 b and 8 c illustrate the flow of requests and responses through the system of FIG. 2 using the process of FIG. 7.

DETAILED DESCRIPTION

[0021] According to one aspect of the invention, a method for load balancing web site resources in an environment where traffic is encrypted will now be described. Referring now to FIG. 2, a block diagram illustrating exemplary components that may be included in such a system is shown.

[0022] In FIG. 2, a system 10 is shown to include a plurality of web site data centers 120 a-120 c coupled to a client 110 via network 130. Each web site 120 a-120 c represents a data center for storing resources that are available to the client. For the purposes of this application, at least a portion of the resources are mirrored at each of the web sites.

[0023] Each data center is shown to include a number of components that are used to manage and deliver streaming media content to a coupled client in an efficient manner. Exemplary components that may be included in the data center include a content director (CD) 100 and one or more content servers 102. One function of the content director is to perform load balancing of resource requests across the various data centers that are coupled to the network. It should be noted that the server performance could be further accelerated through the inclusion of a cache device, coupled to the switch, although the present invention is not limited to any particular memory service configuration.

[0024] The CD 100 and content servers 102 are shown coupled to a switch 106, which controls access to the network 130. Although a switch is shown, it should be understood that any set of devices typically used to connect to a network could alternatively be used, and the present invention is not limited to the use of any particular network connection device. In one embodiment, a content manager 108 is coupled to the switch to provide system management, content management and accounting management features.

[0025] Each Content Director constantly communicates with the other CDs in the network over a TCP/IP connection. In one embodiment, the CDs use a specific protocol referred to as an Interbox Protocol (IBP), although other types of TCP/IP messaging may be used and the present invention is not limited to the use of any specific protocol for communication between CDs. The various data that is exchanged between the CDs includes redirect message (for directing requests for a resource received at one CD to another CD that stores a copy of the resource) and time-stamp information (to allow each CD to monitor the clock of the other data centers for synchronization of operations). As the number of data centers increases, the volume of IBP traffic may impede system efficiency. Thus, according to one embodiment of the invention, the data centers are grouped into global domains and local domains. A global domain includes one or more local domain data centers. When a request is received for a resource, DNS resolves the request to any one of the local domains within the global domain. However, it may be that the local domain selected is not the optimal data center to service the request (whether due to proximity, load, or other factors). The Content Directors, upon receiving the client request, redirect the request to the ‘best’ local domain within the global domain using any number of methods, such as the footrace method described with regard to FIG. 1.

[0026] However, a problem arises in using the footrace method of FIG. 1 when traffic is encrypted. Encryption of networked data has increased because in today's computing environment, the connection between a client and any other point may be routed through dozens of connections. Through spoofing, snooping and general eavesdropping, unauthorized users find it relatively easy to obtain personal client information, such as credit card numbers, social security numbers, etc. As such, security measures have been developed to maintain client privacy. One of the security protocols that is typically used is the Secure Socket Layer (SSL) protocol.

[0027] The SSL protocol operates as follows. When a client and server communicate, SSL ensures that the connection is private and secure through encryption and authentication. Authentication confirms that the server and the client are who they say they are, and have the proper authority to access the information. Encryption creates a secure tunnel between the client and server by encrypting the data and through the use of keys that each end uses to encrypt and decrypt the data. As a result, any unauthorized user who obtains the data but does not have the key will be unable to read what is viewed.

[0028] An SSL protocol is actually comprised of two protocols; the SSL Handshake protocol and the SSL Record protocol. A transaction consists of two distinct parts: the key exchange and the bulk data transfer. The SSL Handshake Protocol handles the key exchange and the SSL Record Protocol handles the bulk data transfer.

[0029] In FIG. 3 a functional flow diagram is provided to illustrate the interplay between the client and server during SSL handshake. At step 40 the client initiates the handshake by requesting an SSL session with the server. The server, receiving the request transitions from a wait state 50, and at step 52 forwards its digital certificate 55 to the client. The digital certificate contains information about the web server, including the server's public key. When the certificate is received, the client checks its validity at step 44 to verify that the certificate is valid (i.e., verifies that it is current and issued by a trusted third party Certificate of Authorities). If the certificate is not valid, the process returns to step 40 to obtain another certificate. If it is valid, then at step 46 the client generates a 48 byte master secret. The secret is encrypted using the server's public key. The encrypted master secret 45 is then forwarded to the server. Upon receiving the master secret from the client, the server then decrypts the master secret using the server's private key. Both the client and the server both have the same master secret at this point, and they use this master secret to create keys for the encryption and MAC algorithms.

[0030] Once both the client and server have the same encryption and MAC keys, they use known SSL encryption and authentication mechanisms to create and encrypted tunnel. Through the encrypted tunnel, they can now pass data securely through the internet.

[0031] As mentioned in the background, a problem arises when attempting to determine the optimal web site for servicing client requests when the traffic is encrypted using protocols such as the SSL protocol. This is because, as described above, the tunnel is generated between a specific server and client pair. Generally speaking, in order for any other web site to communicate with the client, a similar tunnel should be built between the two. Such a solution is time consuming, and, due to the numerous steps involved in setting up the tunnel, would make it difficult to discern optimal web site for servicing client requests in a timely manner.

[0032] However, according to one aspect of the present invention, a system is provided for allowing a mirrored web site to forward encrypted packets to a client without having previously established a tunnel between the web site and the client. This system can be used for two alternative purposes. First, it can be used to seamlessly redirect encrypted requests from a failing web site to an alternative web site in a manner that is transparent to the client. As a result, client requests can be serviced without delay, error messages, or the need to re-establish a new secure session. In addition, the system can also be used to select an optimal web site for servicing client requests using the footrace method discussed above in FIG. 1 using encrypted traffic.

[0033] Referring now to FIG. 4, certain components that may be included in the Content Director 100 to implement load balancing of encrypted traffic are shown. The CD 100 is shown to include a processor 152, coupled to a database 154. The processor communicates via a network interface 155 to switch 106, or via a command line interface 156 to the content manager 108 or a network administrator via graphical user interface (GUI). The command line interface (CLI) allows the administrator to define the global domains of which the data center is a member. In addition, it also allows the local domains in the global domain to be identified. In FIG. 4, a database is shown coupled to the processor, in which this data is shown, although the data may be stored in any location that is accessible to the CD. Also shown in FIG. 4 is a packet builder 55. The packet builder is shown as a distinct entity to represent its functionality, although it should be understood that the packet builder is advantageously implemented in a combination of hardware and software to build an encapsulated packet as will be described below. Also included in the CD is key data storage 57.

[0034] The key data storage 57 provides the packet builder 55 with key data for encrypting packets, thereby enabling a CD to internally build encrypted packets for each of the other CDs in its global domain. According to one aspect of the invention, a packet may be pre-built at a first CD, encrypted using the key data that the first CD received when establishing a tunnel with the client, and encapsulated in a communication to a second CD in the same global domain. The second CD recognizes that it is a pre-built packet for the client, strips off header information from the first CD identifying it as such, and forwards the encrypted packet to the client.

[0035] Providing a mechanism for a CD to communicate encrypted data to a client without having previously established a tunnel between the particular site and the client provides at least two advantages over the prior art. In the prior art, in the event that a resource becomes unavailable at a first data center, a client has to break down the tunnel with the first data center and build a tunnel with the mirror data center, thereby incurring a delay in obtaining access to the resource. With the invention, the first data center can easily redirect all requests from a client to the mirrored site. Security concerns can be addressed in the background without interrupting the user's access to the resource. Thus the present invention provides a mechanism for disaster recovery.

[0036] An example of how the system may work to provide disaster recovery in the event of a server farm failure at Site A is shown in FIGS. 5 and 6. At step 162, the client establishes TCP connection and completes SSL handshake after site selection (using, for example, the site selection method described below in FIGS. 7 and 8a-8 c). At step 164, the CD at site A detects a server farm failure. In the event of a subsequent request by the client to a resource serviced by site A, site A, at step 167 site A decrypts the request and at step 168 examines the address of the request to identify the global domain of the resource. The CD at site A can then examine its database of local domains associated with the global domains to determine whether there is another local domain that can service the request for the resource. If at step 168 the CD at site A determines that there is no other site, then an error message is returned to the client. Otherwise, at step 172 site A forwards the request to the alternative local domain.

[0037] According to one aspect of the invention, the CDs in each global domain additionally use the IBP to exchange the SSL Session state information required for the alternative site to service the request. Thus, assuming that site B is the alternative site selected, site A forwards the SSL state information for decrypting and encrypting the request to site B. At step 172, site B decrypts the forwarded packet and forwards it to its associated server (or cache) for service. When the content is retrieved, the CD, at step 174, encrypts the content and forwards it directly back to the client. Subsequent traffic flows in a triangular pattern, with requests being made by the client to site A, B and back to the client until either the problem at site A is repaired, or an opportunity exists to tunnel directly to site B.

[0038] A second advantage of the present invention is that it allows the footrace method of determining client proximity to be performed even when the clients' requests are encrypted. The footrace may be performed as shown in FIGS. 7 and 8a-8 c.

[0039] At step 182 the client establishes a TCP connection for a global address and a DNS resolves to a web site, for example web site A (hereinafter also referred to! as the synchronizing web site). The client then establishes a secure connection to web site A. Subsequently, at step 184 the client issues a request for resource stored at web site A, but mirrored at alternative sites. At step 186, the synchronizing CD performs expression matching on the global domain name to identify the corresponding local domains in its database (‘participating sites’). At step 188, for each participating site, the CD builds a redirect packet. When building the packet, the CD inserts the local domain name of the associated participating site into the redirect packet and encrypts the packet using the SSL Session ID and keys established with the client during the SSL handshake. The CD then encapsulates the redirect packet into a TCP/IP packet directed to the participating web site, and forwards it to that site. The header of the TCP/IP packet is encoded to identify the packet as an encrypted redirect packet to be used in a footrace, a client address, and a time at which the participating site is to forward the redirect packet to the client address. At step 190, each participating site decodes the TCP/IP header, identifies the packet as an encapsulated redirect, and extracts the redirect packet. At the time indicated by the synchronizing site, each participating site forwards the redirect packet to the client.

[0040] When the client receives its first redirect packet, at step 192 it closes the TCP session with the synchronizing CD, and initiates a new, secure connection to the local domain indicated in the first redirect packet received.

[0041] Accordingly, a system that enables load balancing of encrypted traffic has been described. The system may be used to provide disaster recovery, or alternatively to identify an optimal data center for servicing client requests. It should be noted that, although the above description has included discussion of the SSL protocol, the present invention may be used for any type of encrypted traffic, and the present invention should not be limited to the use of any specific security protocol.

[0042] Having described several embodiments of the invention, it should be understood that various modifications may be made within the spirit and scope of the invention, and the invention, therefore, should only be limited by the claims. 

What is claimed is:
 1. A method of balancing accesses to a resource in a network having encrypted traffic including the steps of: storing, at a first web site having storing the resource, an address of another web site storing a copy of the resource; receiving, at the first web site, a request from a client for the resource, the step of receiving including receiving data enabling secure communication with the client; forwarding, by the first web site, a redirect packet to the another web site, the step of forwarding including the step of modifying the redirect packet using the data enabling secure communication with the client.
 2. The method according to claim 1, further including the step of forwarding, with the redirect packet, a time stamp indicating a time for the another web site to forward the redirect packet to the client.
 3. The method according to claim 2, wherein the redirect packet includes a field identifying a source of the packet, and wherein the step of forwarding includes the step of building the redirect packet by inserting an address of the another web site in the field identifying the source of the packet.
 4. The method of step 3 wherein the redirect packet is a first redirect packet, the method further including the step of forwarding, by the first web site, a second redirect packet to the first web site including the step of building the second redirect packet by inserting an address of the first web site in the field identifying the source of the packet.
 5. The method according to claim 4, further comprising the step of the first web site and the another web site forwarding the second redirect packet and the first redirect packet, respectively, to the client at a time indicated in the time stamp field of the second redirect packet and second redirect packet, respectively.
 6. The method according to claim 5 further comprising the steps of: receiving, by the client, a redirect packet, the received redirect packet including a source field identifying a source of the redirect packet; and the client forwarding subsequent requests for the resource to a web site indicated in the source field of the received redirect packet.
 7. A data center storing a plurality of resources, the data center comprising: a table for storing, for at least one resource, an address of an alternate data center storing a copy of the resource; an interface for establishing a secure communication path with a client device; and a storage mechanism for storing data enabling secure communication with the client device; and a packet builder for building redirect packets for the mirrored web site, the redirect packets comprising the address of the alternate data center and being modified by the data enabling secure communication with the client device. 